| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CPS.2.7.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.2.7 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CPS_2_7_Support_Patient_Data_Derived_from_Eligibility__Formulary_and_Benefit_Documentation_for_Electronic_Prescribing |
| Title | CPS.2.7 Support Patient Data Derived from Eligibility, Formulary and Benefit Documentation for Electronic Prescribing (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Capture and explicitly label patient data derived from eligibility, formulary and benefit information; and link the data source with that data. |
| Purpose | Sources of eligibility, formulary and benefit may provide data for entry into the electronic prescribing or be given a mechanism for entering this data directly. The data must be explicitly labeled as derived from eligibility, formulary and benefit information. Patient data that is derived from eligibility, formulary and benefit data may be provided by: - a provider - a payer, or - entities that transmit or process eligibility, formulary and benefit data. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Capture and explicitly label patient data derived from eligibility, formulary and benefit information; and link the data source with that data.
Sources of eligibility, formulary and benefit may provide data for entry into the electronic prescribing or be given a mechanism for entering this data directly. The data must be explicitly labeled as derived from eligibility, formulary and benefit information. Patient data that is derived from eligibility, formulary and benefit data may be provided by:
| CPS.2.7#01 | SHALL |
The system SHALL provide the ability to manage patient data derived from eligibility, formulary and benefit information. |
| CPS.2.7#02 | SHOULD |
The system SHOULD provide the ability to capture the source of patient data derived from eligibility, formulary and benefit information. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CPS.2.7",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Capture and explicitly label patient data derived from eligibility, formulary and benefit information; and link the data source with that data.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Sources of eligibility, formulary and benefit may provide data for entry into the electronic prescribing or be given a mechanism for entering this data directly. The data must be explicitly labeled as derived from eligibility, formulary and benefit information. Patient data that is derived from eligibility, formulary and benefit data may be provided by:</p>\n<ul>\n<li>a provider</li>\n<li>a payer, or</li>\n<li>entities that transmit or process eligibility, formulary and benefit data.</li>\n</ul>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.7#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage patient data derived from eligibility, formulary and benefit information.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.7#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture the source of patient data derived from eligibility, formulary and benefit information.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.2.7",
"version" : "2.1.0",
"name" : "CPS_2_7_Support_Patient_Data_Derived_from_Eligibility__Formulary_and_Benefit_Documentation_for_Electronic_Prescribing",
"title" : "CPS.2.7 Support Patient Data Derived from Eligibility, Formulary and Benefit Documentation for Electronic Prescribing (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Capture and explicitly label patient data derived from eligibility, formulary and benefit information; and link the data source with that data.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Sources of eligibility, formulary and benefit may provide data for entry into the electronic prescribing or be given a mechanism for entering this data directly. The data must be explicitly labeled as derived from eligibility, formulary and benefit information. Patient data that is derived from eligibility, formulary and benefit data may be provided by: \n- a provider \n- a payer, or \n- entities that transmit or process eligibility, formulary and benefit data.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.2.7-01",
"label" : "CPS.2.7#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage patient data derived from eligibility, formulary and benefit information."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.2.7-02",
"label" : "CPS.2.7#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture the source of patient data derived from eligibility, formulary and benefit information."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.